fix(tsconfig,jsconfig): add missing ES2022.Regexp and ES2023.Intl lib entries#5643
Merged
madskristensen merged 2 commits intoApr 30, 2026
Conversation
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5152
What
TypeScript ships
es2022.regexp.d.tsandes2023.intl.d.tsas separate lib files, but neither is listed in thecompilerOptions.libenum in the tsconfig.json or jsconfig.json schemas. This causes false validation errors when users set"lib": ["ES2022.Regexp"]or"lib": ["ES2023.Intl"]in their tsconfig/jsconfig.Changes
Both
src/schemas/json/tsconfig.jsonandsrc/schemas/json/jsconfig.json:"ES2022.Regexp"after"ES2022.Object"(alphabetical order)"ES2023.Intl"after"ES2023.Collection"(alphabetical order)Verification
TypeScript lib source confirms both files exist:
The maintainer also noted in issue #5152 that jsconfig.json would need the same fix.